docs: add a GitHub Actions section for publishing to Confluence - #46
Merged
Conversation
Document running markfluence in CI to keep Confluence pages in sync with repo markdown: credentials via secrets/variables, a push-triggered workflow that installs from source (go install) and runs `update`, and notes on --force, exit codes, and write permissions. Links to the reusable-action tracking issue (#29).
Store all three settings as secrets, use a single-document publish example with an explicit --page-id, and trim the notes to the essentials.
willkg
force-pushed
the
docs-github-actions
branch
from
July 23, 2026 20:21
877abee to
ead7465
Compare
Reflect the new build stamp (markfluence VERSION (SHA, DATE)) that landed in #45; note it matches `markfluence --version`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a GitHub Actions section to the README showing how to run markfluence in CI to keep Confluence pages in sync with markdown in the repo.
Covers:
CONFLUENCE_TOKENas an encrypted secret,CONFLUENCE_URL/CONFLUENCE_USERNAMEas variables or secrets; markfluence reads them straight from the environment (no.envin CI).actions/setup-go→go install→markfluence update docs/**/*.md --force, with apaths:filter and aconcurrencygroup to avoid overlapping publishes.--force(fresh-checkout mtimes defeat the skip-unchanged heuristic) and how to scope to changed files instead; non-zero exit on failure and the--jsonoption; andcontents: writeonly if a workflow runscreateand commits the persistedpage_idback.Install is via
go install github.com/mozilla/markfluence@latest(with a note to pin a tag once releases exist) because no release binaries are published yet. Links to #29 (reusable action) as the follow-up.Docs-only change.